Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle City Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

High Gosforth Park

reference
1995/017.W3
name
High Gosforth Park
tree-preservation-order

undefined

1995/017
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.606066 55.039495,-1.606667 55.039550,-1.606725 55.039371,-1.606777 55.039200,-1.606814 55.039094,-1.606883 55.038876,-1.607181 55.037985,-1.607216 55.037887,-1.607260 55.037748,-1.607279 55.037697,-1.607299 55.037635,-1.607395 55.037588,-1.607508 55.037520,-1.607561 55.037479,-1.607591 55.037441,-1.607611 55.037391,-1.607606 55.037336,-1.607590 55.037276,-1.607549 55.037230,-1.607506 55.037207,-1.607416 55.037183,-1.607298 55.037174,-1.607185 55.037173,-1.607010 55.037177,-1.606900 55.037217,-1.606842 55.037269,-1.606815 55.037303,-1.606806 55.037362,-1.606806 55.037387,-1.606808 55.037390,-1.606805 55.037421,-1.606821 55.037472,-1.606867 55.037514,-1.606919 55.037557,-1.606934 55.037586,-1.606833 55.037873,-1.606770 55.038065,-1.606467 55.038960,-1.606434 55.039003,-1.606399 55.039036,-1.606364 55.039057,-1.606340 55.039075,-1.606253 55.039131,-1.606166 55.039121,-1.606037 55.039116,-1.605938 55.039116,-1.605877 55.039129,-1.605853 55.039186,-1.605859 55.039253,-1.605959 55.039353,-1.606072 55.039479,-1.606066 55.039495)))
point
POINT (-1.606804 55.038381)
notes
These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date
2022-07-01
start-date
1995-01-01
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL